@ChrisMBarr, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.

Thanks, Microsoft Pull Request Bot

@ChrisMBarr wanted to let you know that the appveyor build is failing because it is brand new. My PR #350 is addressing this by introducing a proper appveyor configuration; until then, you can safely ignore these failures.

This change doesn't actually fix the problem, right? When you initially clone the repo there is not yet a .gitattributes file so you'll get the files using your default line endings. This is why the README asks that you clone the repo with this command:

git clone [email protected]:Microsoft/tslint-microsoft-contrib.git --config core.autocrlf=input --config core.eol=lf

I guess I can commit this, but it doesn't really fix the problem when cloning the repo.

In other words, I think your changes here will "Ensure LF line endings are used upon a git pull" but they will not "Ensure LF line endings are used upon git checkout".

Ah ok, that makes sense. My process here was to:

1. pull
2. get lint errors
3. make the commit in this PR
4. follow these instructions
   • run git rm --cached -r .
   • run git reset --hard

Doing all of that worked for me.

If you don't clone with the right parameters then you're going to need to do the --cached --hard thing regardless.